翻訳と辞書
Words near each other
・ "O" Is for Outlaw
・ "O"-Jung.Ban.Hap.
・ "Ode-to-Napoleon" hexachord
・ "Oh Yeah!" Live
・ "Our Contemporary" regional art exhibition (Leningrad, 1975)
・ "P" Is for Peril
・ "Pimpernel" Smith
・ "Polish death camp" controversy
・ "Pro knigi" ("About books")
・ "Prosopa" Greek Television Awards
・ "Pussy Cats" Starring the Walkmen
・ "Q" Is for Quarry
・ "R" Is for Ricochet
・ "R" The King (2016 film)
・ "Rags" Ragland
・ ! (album)
・ ! (disambiguation)
・ !!
・ !!!
・ !!! (album)
・ !!Destroy-Oh-Boy!!
・ !Action Pact!
・ !Arriba! La Pachanga
・ !Hero
・ !Hero (album)
・ !Kung language
・ !Oka Tokat
・ !PAUS3
・ !T.O.O.H.!
・ !Women Art Revolution


Dictionary Lists
翻訳と辞書 辞書検索 [ 開発暫定版 ]
スポンサード リンク

software requirements specification : ウィキペディア英語版
software requirements specification

A software requirements specification (SRS) is a description of a software system to be developed, laying out functional and non-functional requirements, and may include a set of use cases that describe interactions the users will have with the software.
Software requirements specification establishes the basis for an agreement between customers and contractors or suppliers (in market-driven projects, these roles may be played by the marketing and development divisions) on what the software product is to do as well as what it is not expected to do. Software requirements specification permits a rigorous assessment of requirements before design can begin and reduces later redesign. It should also provide a realistic basis for estimating product costs, risks, and schedules.
The software requirements specification document enlists enough and necessary requirements that are required for the project development. To derive the requirements we need to have clear and thorough understanding of the products to be developed or being developed. This is achieved and refined with detailed and continuous communications with the project team and customer till the completion of the software.
The SRS may be one of a contract deliverable Data Item Descriptions
〕 or have other forms of organizationally-mandated content.
== Structure ==
An example organization of an SRS is as follows:
*Introduction
*
*Purpose
*
*Definitions
*
*System overview
*
*References
*Overall description
*
*Product perspective
*
*
*System Interfaces
*
*
*User Interfaces
*
*
*Hardware interfaces
*
*
*Software interfaces
*
*
*Communication Interfaces
*
*
*Memory Constraints
*
*
*Operations
*
*
*Site Adaptation Requirements
*
*Product functions
*
*User characteristics
*
*Constraints, assumptions and dependencies
*Specific requirements
*
*External interface requirements
*
*Functional requirements
*
*Performance requirements
*
*Design constraints
*
*
*Standards Compliance
*
*Logical database requirement
*
*Software System attributes
*
*
*Reliability
*
*
*Availability
*
*
*Security
*
*
*Maintainability
*
*
*Portability
*
*Other requirements

抄文引用元・出典: フリー百科事典『 ウィキペディア(Wikipedia)
ウィキペディアで「software requirements specification」の詳細全文を読む



スポンサード リンク
翻訳と辞書 : 翻訳のためのインターネットリソース

Copyright(C) kotoba.ne.jp 1997-2016. All Rights Reserved.